Digital.ai Agility is a great product for tracking the work of software teams
We use Digital.ai Agility extensively to track all the work done by our scrum teams. We have 6 feature teams that use this on a daily …
Overview
What is Digital.ai Agility?
Digital.ai Agility (formerly VersionOne) helps organizations harness the power of their people’s knowledge, processes, and technology to build agile practices that scale across the enterprise. Its capabilities enable organizations to align products and investments with strategic business goals by coordinating…
Recent Reviews
Reviewer Pros & Cons
Pricing
N/A
Unavailable
What is Digital.ai Agility?
Digital.ai Agility (formerly VersionOne) helps organizations harness the power of their people’s knowledge, processes, and technology to build agile practices that scale across the enterprise. Its capabilities enable organizations to align products and investments with strategic business goals…
Entry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Would you like us to let the vendor know that you want pricing?
10 people also want pricing
Alternatives Pricing
What is Jira Software?
Jira Software is a project management tool from Atlassian, featuring an interactive timeline for mapping work items, dependencies, and releases, Scrum boards for agile teams, and out-of-the-box reports and dashboards.
What is Wrike?
Wrike is a project management and collaboration software. This solution connects tasks, discussions, and emails to the user’s project plan. Wrike is optimized for agile workflows and aims to help resolve data silos, poor visibility into work status, and missed deadlines and project failures.
Product Demos
Managing Users in Digital.ai Agility
YouTube
Product Details
- About
- Tech Details
What is Digital.ai Agility?
Digital.ai Agility (formerly VersionOne) helps organizations harness the power of their people’s knowledge, processes, and technology to build agile practices that scale across the enterprise. Its capabilities enable organizations to align products and investments with strategic business goals by coordinating planning, tracking, and reporting work across large distributed companies. Digital.ai Agility connects business strategy with team execution, providing a unified view at all levels, from the portfolio to teams. It helps everyone from executives to developers collaborate, communicate, and gain visibility within a single environment.
CollabNet merged with VersionOne in 2017, and merged with XebiaLabs and Arxan in April 2020.
Digital.ai Agility Technical Details
| Operating Systems | Unspecified |
|---|---|
| Mobile Application | No |
Comparisons
Compare with
Reviews and Ratings
(42)
Community Insights
TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!
- Business Problems Solved
- Pros
- Cons
- Recommendations
VersionOne has gained popularity as a preferred alternative to Jira for implementing the Scaled Agile Framework SAFe, primarily due to its robust support for SAFe functionalities. Users have found VersionOne to be highly versatile, allowing easy configuration to accommodate any SAFe configuration. At the team level, teams rely on VersionOne for various activities such as release planning, sprint planning, test management, and active collaboration, especially for distributed teams. The team rooms and planning features provided by VersionOne have proven to be valuable in keeping teams focused and enabling progress tracking. Product Owners appreciate the ability to enter user stories directly into VersionOne, seamlessly integrating it into the software development lifecycle process. Moreover, VersionOne offers extensive capabilities in sprint and release planning, backlog maintenance, defect tracking, collaboration, and notifications, making it an indispensable tool for voting and coordination across multiple locations and teams. Its widespread adoption across organizations is evidence of its effectiveness in managing tasks, tracking project progress, and implementing Agile processes. Leaders and stakeholders benefit from real-time collaboration, project analysis, and access to critical metric data for workload distribution, resource allocation, and project estimations. Additionally, VersionOne supports various needs within different departments of an organization including charting progress with burndown charts, enabling retrospection for continuous improvement, tracking bugs for quality assurance purposes, and providing project management capabilities across multiple teams.
Conversations Feature: Users have found the Conversations feature in Version One particularly helpful for distributed teams, with some reviewers stating that it enhances collaboration and transparency among stakeholders.
Visualization Feature: The Visualization feature in Version One has been appreciated by users as it enables tracking forward and backward dependencies. Several reviewers mentioned that this feature helps them understand how stories are related and identify blocking issues.
Integration with GitHub: Many users highly value the integration of Version One with GitHub. They have stated that this integration automatically updates the build version to the story on Version One whenever a new build is triggered, eliminating the need for manual communication and keeping everyone updated effortlessly.
Complicated Setup Process: Several users have found the setup process of VersionOne to be complicated compared to other tools. They have expressed difficulties in getting started and setting up the software.
Lack of Customization Options: Some reviewers have mentioned that customization options in VersionOne are lacking, especially when compared to Jira. This limitation makes it difficult for teams to tailor the software according to their specific requirements and workflows.
Slow Performance with Attachments: Users have expressed frustration with the slow performance of VersionOne, particularly when dealing with stories that have tests or documents attached to them. The sluggishness negatively impacts productivity and efficiency for these users.
Based on user reviews, here are three common recommendations for VersionOne:
-
Thoroughly research and consider all options before making a decision. Users suggest doing thorough research and considering all available options before choosing VersionOne as their Agile development tool. This recommendation highlights the importance of evaluating different tools to ensure they meet specific needs and requirements.
-
Try the product's reporting capability first. It is recommended to explore the reporting capability of VersionOne as a starting point. Users found this feature beneficial for tracking progress in Agile development and obtaining valuable insights. By utilizing the reporting functionality, teams can gain visibility into their projects and make data-driven decisions.
-
Consider alternative options such as JIRA or Pivotal Tracker. Some users recommend exploring other tools like JIRA or Pivotal Tracker before deciding on VersionOne. These alternatives are mentioned for their modern UI, simpler feature set, and compatibility with Agile methodologies. This suggestion emphasizes the importance of evaluating multiple tools to find the best fit for specific needs and preferences.
Attribute Ratings
Reviews
(1-4 of 4)Companies can't remove reviews or game the system. Here's why
February 03, 2020
CollabNet VersionOne is exceptional
CollabNet VersionOne is widely used in our business by various business units. The problem that business units face without VersionOne are;
1. Multiple duplications of work
2. Project work tracking can be inaccurate.
Using this application enables real-time collaboration of multiple teams, Overview of project or backlog items, sprint by sprint analysis. These are critical metric data points that can help future workload distribution, resource allocation, and overall future project estimations. As a leader, this application gives me access to all my teams' work and progress. It is also useful when collecting metrics that help stakeholders in project increment planning.
1. Multiple duplications of work
2. Project work tracking can be inaccurate.
Using this application enables real-time collaboration of multiple teams, Overview of project or backlog items, sprint by sprint analysis. These are critical metric data points that can help future workload distribution, resource allocation, and overall future project estimations. As a leader, this application gives me access to all my teams' work and progress. It is also useful when collecting metrics that help stakeholders in project increment planning.
- Automated saving of changes, no records can be lost because all items are saved in real-time.
- The watch function, optional but beneficial when managing multiple teams or projects.
- An optional presentation mode could be good for multi-site
- Built-in snipping tool
- Not involved in the ROI analysis
- Atlassian JIRA Align (formerly AgileCraft)
These two are close; however, CollabNet VersionOne offers more flexibility and control. Admin users have a wider variety of customization options and integration with 3rd party applications
VersionOne is what our teams use track stories and plan our sprints across over 25 sprint teams in multiple locations including Seattle, WA, San Francisco, CA, San Jose, CA, Ottawa, Canada, and Bucharest, Romania. Using VersionOne we are able to plan and coordinate to deliver our complex solution to our customers.
- VersionOne makes it easy to create stories and move them across teams, as needed.
- VersionOne's team view gives the team a clear view of the work to be done, work in progress, and work completed. This is particularly useful to have as a visual aid in stand ups or during reviews.
- VersionOne allows the team to track capacity and work for each story which is useful to determining if the story is still on track.
- Saving of changes is inconsistent. Sometimes the changes appear to save automatically and other times the user needs to click the "Apply" button. Until the user is familiar with when this needs to happen, work can easily be lost.
- This may be a setup configuration issue, but it would be good to be able to set the default team when creating stories. Too often stories are created and the user forgets to enter the team and they need to search the entire database for the story that was just created.
- The ramp up took a lot of man hours, but once we all learned it, I think it went much more smoothly. I think roll out has a big impact on this. If a team had set this up with Epics and rolled it out to the teams to fold our stories into it instead of everyone figuring it all out at the same time, it would have been less headache for all of the team members and less time and money spent. I don't have specific numbers since I am not part of that side of the business.
- On the positive side, this did allow all our teams to coordinate better in one organizing tool. It doesn't work as well for teams who work better with Kanban, but it still allows visibility across all the teams.
JIRA appears to be more extensible with the ability for Scrum, Kanban, bug/incident tracking, and the ability to customize dashboards. However, VersionOne's performance over the same teams is extremely fast in comparison and therefore allows users to be more productive over the same amount of time.
We use Version One across our entire organization. As a web design and digital marketing firm, it helps us to manage tasks and track progress, and it enables us to more easily implement Agile processes. Our organization is somewhat new to Agile, and Version One makes it easier to keep us on track.
- Assigning backlogs is simple once you're in a project. The ability to add backlogs in line is helpful when you just want to list out new backlogs before adding your user stories.
- The ability to sort by different types of data, so that you only view exactly what you want to see is very helpful, especially during sprint planning meetings.
- The customizability of the app enables the user to adjust certain criteria based on their team's needs. For example, adjusting sprint length.
- As a whole, Version One is not user-friendly. Without an intense familiarity of the app, it's often difficult to find things you're looking for. Given the complex reality of the customizability, I'm not sure if there's a way to make the interface simpler.
- I would like the ability to add attachments and imbedded images more simply within user stories. Sometimes, It'd be helpful to have the ability to add a screenshot of a page at specific points within your user story.
- From the Version One homepage, there is no clear CTA for users to login.
- It has made it easier to implement Agile processes. Since our team is fairly new to Agile, this has been extremely helpful.
- Our organization is quickly growing, and V1 has made it easier for new hires to look at everything that our team has in the works.
Basecamp functions much differently from Version One and serves a different purpose, so it's kind of like comparing apples and oranges. However, both V1 and Basecamp have their pros and cons. V1 makes it easier to manage Agile processes, but Basecamp is more user-friendly and can be used for broader purposes. At our organization, we utilize both products. V1 is what we use to manage processes internally, and Basecamp is what we use to manage client-facing processes. If our organization wasn't Agile, I would prefer to use Basecamp for all project management (internal and client-facing), and have done so at previous organizations for which I've worked.
August 01, 2016
Giving VersionOne a goodbye kiss
Aaron's has used VersionOne for years (well before my time here) across the entire IT organization. VersionOne was/is used for project management, sprint tracking, defect and backlog records, and test case management.
- Storyboard view
- Ability to customize fields in backlogs and defects
- Ease of learning the tool
- VersionOne speed is not the best and is not consistent
- The Search function could be better, it returns a TON of clutter
- Test case management is poor, to the point where no one here recommends VersionOne for test
- No drag and drop capability for attachments
- Text editor has real problems, limited formatting, balky pasting of images
- I came in near the end of our use of VersionOne (we are migrating to JIRA), and I don't operate or think at the business return (ROI) level. I'm not the one to comment on this!
- I suspect that V1 added much clarity to the prioritization of work, and added visibility across entire teams. So I assume that it had a positive impact on returns.